iLoADER |
HOME |
Control FileThe Control File is produced once all of the relevant data files have been copied into the Data Load Repository. It controls the sequence of the load process and references all of the files copied onto the server for loading. The name of the Control File is defined in the scriptset configuration process and stored in the registry. When running scripts, iLoader checks for the presence of a Control File that contains information regarding the data to be loaded. This file must be created in the Scripts directory after the related data files have been placed into the Data Load Repository directory. Default scripts are automatically added to the Scripts file when it is created. The Control File contains the scripts that are available, in the format:
You can view and edit the contents of the Control File from the Scripts tab, the Table Declaration and Importers buttons are activated. When you create and save a new configuration, the following information is added to the Control file: DO_PRELOADSCRIPT=TRUE DO_TABLELOADSCRIPT=TRUE DO_LINKSCRIPT=TRUE DO_METADATASCRIPT=TRUE DO_POSTLOADSCRIPT=TRUE DO_NEWTABLESONLY=FALSE ENABLE_ROLLBACK=FALSE LOCK_AND_LOAD=FALSE ALLOWMULTIPLESPACES The first five files reference the script files. The next three files set commands to be run before the data load, and the last entry specifies whether to allow the removal of multiple spaces. If the file is set to TRUE, iLoader runs the commands specified in the file. If it is set to FALSE, any commands written in this file are ignored.
For each different table to be loaded, there is a BEGIN TABLE_DECLARATION and an END TABLE_DECLARATION. In some cases, one data file may supply two tables and therefore the data file will be referenced twice. |
Online & Instructor-Led Courses | Training Videos | Webinar Recordings | ![]() |
|
![]() |
© Alterian. All Rights Reserved. | Privacy Policy | Legal Notice | ![]() ![]() ![]() |